Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TC 2.0.9 #483

Merged
merged 10 commits into from
Nov 12, 2024
Merged

TC 2.0.9 #483

merged 10 commits into from
Nov 12, 2024

Conversation

f-peverali
Copy link
Contributor

@f-peverali f-peverali commented Nov 12, 2024

Version Upgrade Template

Version: 2.0.9

Date:

Description

This is a Pullrequest that requires an increase in the Version number. Therefore, multiple outside-github, related Task have to be performed and checked.

All jobs with an x in the boxes were performed to the best of knowledge.

Pre-Merge Activities

  • This PR refers to a versioned Branch with a name and a version number in the form of N.n.n, e.g. "TC_3.2.1".
  • This PR has a clean meaningful commit history. Minor commits or commits without description have been squashed, at the latest now.
  • Eventually, increase the dependency of to newer Basis Modul and Basispofil-de and possibly others (package json and sushi-config)
  • Run Python script in terminal and increment version
  • New Release Notes were created, alined to the commit history. Possibly, if you want to check the release notes for completeness, check against automatic relesase note generation in GitHub. In Github, go to
    • -> Releases then -> Draft a new release with the Modul Name and Version, then
    • -> Target the main-Branch and -> enter a new Tag according to the Version, then click.
    • Click -> Generate Release notes , -> Adjust them if necessary and -> Copy/Paste the Details in the RealeaseNotes.md of the very Branch you want to merge.
    • Finally -> Save as Draft

Merge and Publishing

  • With the updated Version, Dates, and Release Notes (as described above) with the last committ into the Branch you want to merge.
  • In GitHub -> Actions the -> CI (FHIR Validation) workflow terminates successfully.
  • Add the Approve / the PR gets positively reviewed by a colleague.
  • Merge (without squash) the PR, delete the Branch.

Post-Merge Activities

  • Go to the corresponding SIMPLIFIER Project and -> Github -> Reimport the project.
  • Go to the corresponding SIMPLIFIER Project and -> Packages -> Expand the Dropdown for Create -> Create new package for the project.
    • With the corresponding version number, and
    • The Release notes (from above) and a compare-link to the previous Release.
    • Unlist the old package by -> clicking on the old package, -> go to Administration and -> click on Unlist
  • Publish the previously drafted Release, including version number, on GitHub.
  • Provide / Archive the IG in the corresponding gh-pages branch of the GitHub project.
    • Checkout the Branch (no need to merge it later).
    • Export from Simplifier via -> Guides -> Expand the Modul ... -> Export
    • Unpack the zip, remove the packages folder (because its kinda big), and move everything else to a (version corresponding) new folder in the branch folder structure.
    • Update the file index.html and check rendering.
    • commit the branch.
  • If ISiK Basismodul was updated all depending Modules should be updated with a renewed dependency to the incremented Basismodul version - possibly including and closing technical corrections

Finished

@f-peverali f-peverali changed the title auto-generated file update of TC version by GitHub Actions (CI FSH to… TC 2.0.9 Nov 12, 2024
@f-peverali f-peverali merged commit 667835d into main-isik-stufe-2 Nov 12, 2024
2 checks passed
@f-peverali f-peverali deleted the TC_2.0.9 branch November 12, 2024 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant